Vcenter NamespaceManagement Supervisors Workloads Images Settings UpdateSpec
The Vcenter NamespaceManagement Supervisors Workloads Images Settings UpdateSpec schema contains the specifications for updating how images for Virtual Machines, Kubernetes nodes, and vSphere Pods are synced on a Supervisor's workload components.
This schema was added in vSphere API 9.1.0.0.
{
"registry": {
"hostname": "string",
"port": 0
},
"repository": "string",
"content_libraries": [
{
"content_library": "string",
"supervisor_services": [
"string"
],
"resource_naming_strategy": "string"
}
]
}
The Vcenter NamespaceManagement Supervisors Workloads Images Settings UpdateSpec.registry specifies the default container image registry to use for vSphere Pods when an image is not fully qualified. For example, if this is set to 'my-registry.com' and a Pod uses the image 'nginx:latest', the system will attempt to pull 'my-registry.com/nginx:latest'. This field is ignored for fully qualified images like 'random.registry/nginx:latest'.
This property was added in vSphere API 9.1.0.0.
If missing or null, no registry changes will be made to the Supervisor workload components.
The Vcenter NamespaceManagement Supervisors Workloads Images Settings UpdateSpec.repository specifies the default repository (often a project or namespace) within the registry to use for unqualified vSphere Pod images. For example, if the Vcenter NamespaceManagement Supervisors Workloads Images Settings UpdateSpec.registry is set to 'docker.io' and this field is set to 'library', a Pod using the image 'nginx:latest' will pull from 'docker.io/library/nginx:latest'. This field is ignored for fully qualified images.
This property was added in vSphere API 9.1.0.0.
If missing or null, no repository changes will be made to the Supervisor workload components.
Vcenter NamespaceManagement Supervisors Workloads Images Settings UpdateSpec.content_libraries is a list of Content Libraries that will be associated with a Supervisor's workload components. This list refers to existing Content Libraries in the vSphere inventory. These Content Libraries and the Content Library items belonging to them will be read-only across all vSphere Namespaces, and will be used as images for Virtual Machines and Kubernetes nodes.
This property was added in vSphere API 9.1.0.0.
If missing or null, no changes will be made to the content libraries that are associated with the Supervisor workload components.